External authorization server setup
In some cases it is preferable to have one central authorization server to manage access to many DINGO devices. The external authorization server setup on the DINGO-Stack allows an external authorization server to have the responsibility to generate signed tokens for access to the DINGO device.
The DINGO-Manager does not use this option. It only talks to the internal authorization server, but other clients might prefer it.
Properties
Primary URI: This is the URI to the endpoint for requiring access tokens from the primary authorization server. The clients need this information to know where to get an access token.
Primary certificate: This is the public certificate of the primary server.
Primary public key: This is the public key used to verify the signed tokens from the primary server. The DINGO-Stack will use this key to verify the authenticity of access tokens.
Secondary URI: This is the URI to the endpoint for requiring access tokens from the secondary authorization server. The clients need this information to know where to get an access token if the primary server does not respond.
Secondary certificate: This is the public certificate of the secondary server.
Secondary public key: This is the public key used to verify the signed tokens from the secondary server. The DINGO-Stack will use this key to verify the authenticity of access tokens.
In deployments where there is no redundant backup authorization server, it is recommended that the secondary URI be left blank rather than being set equal to the primary URI to prevent unnecessary client actions.
Press the Save button to save the external authorization setup to the DINGO device.
The reload icon 
in the upper right corner can be clicked to reload the information from the DINGO device.